feat(push): --force flag to skip forge contentHash dedup#38
Merged
Conversation
Threads a new `--force` flag through to the Gradle invocation, which in turn appends `?force=true` to forge's POST /v1/pushes call. Skips the contentHash idempotency lookup so the build pipeline runs even when an identical push already produced an image — useful when the upstream base image moved under a stable tag. Pairs with grounds-push#TBD and grounds-forge#TBD. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
hbrombeer
force-pushed
the
feat/push-force-flag
branch
from
9432cdd to
af18e58
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Threads --force through to gradle invocation. Pairs with grounds-forge + grounds-push --force flags.
🤖 Generated with Claude Code